home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
nwlite
/
faxdoc.exe
/
2907.TXT
< prev
next >
Wrap
Text File
|
1993-05-14
|
14KB
|
318 lines
FYI
(Note: The origin of this information may be internal or external to Novell.
Novell makes every effort within its means to verify this information.
However, the information provided in this document is FOR YOUR INFORMATION
only. Novell makes no explicit or implied claims to the validity of this
information.)
TITLE: Windows 3.0 Compatibility
DOCUMENT ID#: FYI.P.6044
DATE: 04DEC92
PRODUCT: NetWare Lite
PRODUCT VERSION: All versions
SUPERSEDES: NA
LITE FAX DOC #: 2907
SYMPTOM
NA
ISSUE/PROBLEM
Windows 3.0 Compatibility
INSTALLATION
Follow the regular installation procedures for Windows. Normally Windows
will automatically configure itself as if no network is loaded. If you
have NetWare Lite loaded when you install Windows, then Windows will set
itself up for "Microsoft Network (or 100 percent Compatible)."
Putting Windows on a NetWare Lite Network:
The following is intended for users who want to install windows in
shared mode. Most of this information can be found in the Windows
User Guide. The following steps are for the server:
1. Select the Server that you want Windows physically to reside,
and create a directory called WIN30.
2. Insert INSTALL DISK 2 and copy the file called EXPAND.EXE to
the WIN30 directory.
3. Create a BATCH file in the WIN30 directory called EXPALL.BAT
with the following statements:
%1
for %%i in (*.*) do %2\expand %%i %2\%%i
rename %2\*.sy$ *.sys
attrib %2\*.* +r
4. Insert WINDOWS DISK 1 into a floppy drive. Then from the WIN30
directory, run the following:
EXPALL <sourcedrive> <destination directory>
Example: EXPALL A: C:\WIN30
Note: Step 4 must be repeated for each Windows disk.
5. Enter the NetWare Lite menu utility, by typing NET. Then
select "Supervise the network" and then "Network directories."
Create a network directory by pressing the <Insert> key.
Select the server where your WIN30 directory is located, then
enter the path as C:\WIN30.
6. Increase FILES=XX in the CONFIG.SYS file on the server by 20
per client connected.
7. Enter the NET menu utility and select "Supervise the Network"
and then select "Server Configuration." Increase CLIENT
TASKS=XX by 10 per client connected. Reboot.
The following steps are for the client:
1. Load NetWare Lite by typing STARTNET. Map a drive to WIN30:
Net Map I: WIN30 <Enter>
2. Change to the I: drive
I: <Enter>
3. Type SETUP/N, then follow the Windows installation
instructions. Note: At the configuration screen, select the
Network option "Microsoft Network (or 100% Compatible)."
4. Reboot the machine. When you reboot the machine, DOS will give
you the following message:
┌───────────────────────────────────┐
│Search path contains invalid drive.│
└───────────────────────────────────┘
This message will occur any time you run a program and DOS
searches your path. It does this because Windows inserted the
I: drive into your path when it was installed. When the
machine is first booted, the I: drive has not been mapped yet,
so NetWare Lite is unable to locate it. Just ignore the
message. When you map the I: drive to WIN30, the message will
go away. If you want it to disappear, insert the following
line into your AUTOEXEC.BAT file before the path statement:
C:\<DOS directory>\SUBST I: C:
This line will make the I: drive temporarily search the C:
drive, thereby making it a valid statement in the path. As
soon as your map command executes, the I: drive will be
redirected to a network directory.
After you reboot, load the network by typing STARTNET. After
you have you have performed your drive mappings and printer
captures, you can type WIN to enter Windows.
TIPS FOR RUNNING WINDOWS 3.0
Network Operations
Set up the NetWare Lite environment before running Windows (that is
make sure all drives are mapped, printer ports are captured, and
network resources are set up).
Mapped Drives and Connections
Windows will display a message indicating that "drive does not
contain any files" if you try to access a drive on a server that has
gone down. Any attempt to access that drive will fail. Under
regular DOS, this error is trapped and the client saves enough
information to restore automatically the connection to that network
directory when the downed server returns to the network. Windows
prevents regular DOS from trapping this error. To restore
connections to your mapped drive, exit Windows and reissue the NET
MAP command when the server is back on the network. (See Question 2
in the Questions and Answers section of this document for more
information.)
Using Windows to Perform Network Operations
Changing the network configuration in the Windows SETUP from "NO
NETWORK" to "Microsoft Network (100% Compatible)" on a stand alone
machine provides the ability to connect and disconnect network
drives and printers through Windows. However, such operations are
not supported by Novell. Unpredictable problems may occur. Use
"Microsoft Network (or 100% Compatible)" with caution, and if
problems occur, change to "NO NETWORK."
Selecting Printers
If Windows is set up for "NO NETWORK," then Windows does not know
how to handle redirections (such as printer captures and drive
mappings). Consequently, the user should configure the printer in
Windows for either the LPT1.OS2 or the LPT2.OS2 port depending on
what has been captured before entering Windows. (Please see
Question 3 in the Question and Answers section of this document for
more information.)
Browse
The browse function does not work when trying to attach to servers
or trying to capture printers.
NetWare Lite Messages
Messages sent to network users through NetWare Lite will not be
received if the user to whom you are sending the message is in
Windows.
Windows Modes
If you are experiencing a problem that only occurs when NetWare Lite
is loaded and if the problem seems unsolvable, experiment with
various Windows modes to see if the problem is corrected. The
Windows mode can be changed by using one of the following command
line parameters:
Standard Mode: WIN /s
Real Mode: WIN /r
Enhanced Mode: WIN /3
HIMEM.SYS
If you are using MS-DOS 5.0, make sure that you are using the
HIMEM.SYS version (04-09-91) that came with MS-DOS 5.0 and not the
one that came with Windows. Windows 3.0 shipped with a more recent
driver that has proven to be less compatible with MS-DOS 5.0 than
the HIMEM.SYS that DOS is shipped with.
Interrupts
VPICDA.386 is a patch written by Microsoft that fixes problems that
arise when network boards are set to a number greater than 10. It
must also be used if you are using interrupt 2. (Which means
VPICDA.386 does not need to be loaded if you are using any of the
interrupts from 3 to 8.)
Use the following instructions to install VPICDA.386:
1. Dowload WINUP4.ZIP from CompuServe (See Fax Document 2903 or
FYI.P.6087 for information on how to access CompuServe).
2. Unzip the WINUP4.ZIP and copy VPICDA.386 into your
Windows\System directory.
3. Edit SYSTEM.INI file. (Use Notepad or another editor.)
4. Remove the "device=*vpicd" line.
5. Replace it with the "device=VPICDA.386" line.
Base I/O Addresses
I/O addresses below 300 should not be used for network boards on
machines that also use Windows.
Changes to SYSTEM.INI
Make sure that the following line is in the Windows SYSTEM.INI file:
[386Enh]
UniqueDOSPSP = TRUE
Doing this will solve occasional problems with applications that
hang a Windows client.
Speed Issues with NetWare Lite and Windows
See the fax documents concerning the patches that have been released
by Novell that increase printing speed. If your network seems slow,
these patches could solve your problem.
NetWare Lite and Windows: Common Question and Answers.
Question 1: Why does my system receive Sharing Violations or lockups
when running Windows or Windows' applications?
Answer 1: You possibly neglected to set all applications (.EXE,
.COM, and .OVL files) to read-only using the ATTRIB
command. This can be done by executing the following
commands in all directories that might be used across the
network:
attrib +r *.exe
attrib +r *.com
attrib +r *.ovl
Question 2: What happens if my system loses connections while in
Windows?
Answer: 2 If a client loses connections temporarily with a server
while in DOS, then one of two things will happen:
1. The connection will be reestablished by NetWare Lite.
2. The user will try to perform something that requires
a connection and will get an A)bort, R)etry, F)ail
error. If the user presses <F> or <R>, then the
connection will be reestablished.
Unfortunately, Windows will not recognize this "critical
error message" and so will not reestablish connections
when attempting to perform a network operation such as
printing to a network printer. The user must exit out to
DOS, perform a function that will reestablish connections
after the server is back up (such as DIR on a network
directory), then enter Windows again.
Question 3: Why do I have to select LPT1.OS2 when I want to print from
Windows in a "NO NETWORK" mode?
Answer: 3 NetWare Lite is a peer-to-peer network, which means it
runs on top of DOS. When a printer is captured, NetWare
Lite tricks DOS into printing to another location (such as
a printer on another machine). This is why you can print
from an application to an LPT1 port, and the job will end
up at another machine's printer.
Some applications (like Windows) bypass DOS and print
directly to the LPT port. So, if you print from an
application in Windows, it will bypass DOS, which means it
will bypass your capture command and will try to print to
a printer on your client (instead of where you want it to
go). However, you can trick Windows by going into the
WIN.INI file and inserting the following line under the
[Ports] section:
[Ports]
LPT1.XXX= (The suffix can be any three letters.)
For example: LPT1.OS2=
Windows now interprets that a file called LPT1.OS2 is on
your disk; and if you select LPT1.OS2 in "printer setup"
under Control Panel, Windows will try to print to this
"file." When Windows sends a print job to the file
"LPT1.OS2" to DOS, DOS strips off the suffix (OS2, XXX, or
whatever) and sends the job to the redirected printer.
Question 4: Why can't I print using WordPerfect for Windows?
Answer: 4 If WordPerfect printer drivers are being used instead of
Windows', the user needs to make some adjustments to make
WordPerfect work correctly. The adjustments are similar
to the ones made above to Windows. First, go into "select
printer." Instead of selecting LPT1 or LPT2, select file.
Then enter the name of a file that starts with LPT1 or
LPT2:
LPT1.XXX
For example: LPT1.OS2
This will cause WordPerfect to print to LPT1 correctly for
the same reasons it enables Windows to work correctly.
SOLUTION
NA